|
Logjam is a security vulnerability against a Diffie–Hellman key exchange ranging from 512-bit (US export-grade) to 1024-bit keys.〔(【引用サイトリンク】title=The Logjam Attack )〕 It was discovered by a group of computer scientists and publicly reported on May 20, 2015.〔http://www.wsj.com/articles/new-computer-bug-exposes-broad-security-flaws-1432076565〕 Diffie–Hellman key exchange depends for its security on the presumed difficultly of solving the discrete logarithm problem. The authors took advantage of the fact that the number field sieve algorithm, which is generally the most effective method for finding discrete logarithms, consists of four large computational steps, of which the first three depend only on the order of the group G, not on the specific number whose finite log is desired. If the results of the first three steps are precomputed and saved, they can be used to solve any discrete log problem for that prime group in relatively short time. It turns out that much Internet traffic only uses one of a handful of groups that are of order 1024-bits or less. One vulnerability demonstrated by the authors was using a man-in-the-middle network attacker to downgrade a Transport Layer Security (TLS) connection to use 512 bit DH export-grade cryptography, allowing him to read the exchanged data and inject data into the connection. It affects the HTTPS, SMTPS, and IMAPS protocols, among others. The authors needed several thousand CPU cores for a week to precompute data for a single 512-bit prime. Once that was done, however, individual logarithms could be solved in about a minute using two 18-core Intel Xeon CPUs. Its CVE ID is CVE-2015-4000.〔https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000〕 The authors also estimated the feasibility of the attack against 1024 bit Diffie–Hellman primes. By design, many Diffie–Hellman implementations use the same pregenerated prime for their field. This was considered secure, since the discrete log problem is still considered hard for big-enough primes even if the group is known and reused. The researchers calculated the cost of creating logjam precomputation for one 1024-bit prime at hundreds of millions of USD, and noted that this was well within range of the FY2012 $10.5 billion U.S. Consolidated Cryptologic Program (which includes NSA). Because of the reuse of primes, generating precomputation for just one prime would break two-thirds of VPNs and a quarter of all SSH servers globally. The researchers noted that this attack fits claims in leaked NSA papers that NSA is able to break much current crypto. They recommend using primes of 2048 bits or more as a defense or switching to Elliptic curve Diffie–Hellman (ECDH).〔 == Responses == * On May 12, 2015, Microsoft released a patch for Internet Explorer.〔 〕 * On June 16, 2015, the Tor Project provided a patch for Logjam to the Tor Browser.〔https://blog.torproject.org/blog/tor-browser-452-released〕 * On June 30, 2015, Apple released a patch for both OS X Yosemite and iOS 8 operating system.〔 〕〔 〕 * On June 30, 2015, the Mozilla project released a fix for the Firefox browser.〔 (【引用サイトリンク】 publisher=Mozilla ) 〕 * On September 1, 2015, Google released a fix for the Chrome browser.〔 (【引用サイトリンク】title=Stable Channel Updates ) 〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Logjam (computer security)」の詳細全文を読む スポンサード リンク
|